Tab: Log
You can view the PLC log on this tab of the generic device editor. It lists the events that were recorded on the target system. This concerns the following:
Events during the startup and shutdown of the system (components loaded, with version)
Application download and loading of the boot application
Custom entries
Log entries from I/O drivers
Log entries from data sources
Tip
The Log tab also opens when you click the Open Log Page command. You can configure this as a menu command in the Customize dialog.
Tab: Log
![]() | Refreshes the list of log events for all runtime system component |
Components | Filters the display of log events by the runtime system components selected in the list box Example:
<all components>: Displays the reported events of all components |
![]() | Loads the next page with newer log messages |
![]() | Loads the previous page with older log messages |
![]() | Loads the page with the newest log entries and enables automatic scrolling |
![]() |
TipThis is also displayed on the status bar as Auto-Scroll: ON. |
![]() | Loads the page with oldest log messages |
![]() | Filters events with the severity Warning and notifies about how many Blue-outlined button: Warnings are displayed. |
![]() | Filters events with the severity Error and notifies about how many Blue-outlined button: Errors are displayed. |
![]() | Filters events with the severity Exception and notifies about how many Blue-outlined button: Exceptions are displayed. |
![]() | Filters events with the severity Information and notifies about how many Blue-outlined button: Information is displayed. |
![]() | Filters events with the severity Debug and notifies about how many Blue-outlined button: Debug messages are displayed. |
Search in messages | Input field for search text When you enter one or more characters in the search field, the logger messages will highlight the hits in yellow. |
| Jumps to the next hit |
| Jumps to the previous hit |
Logger | Enables a logger for displaying its recorded events By default, the
|
UTC time |
The conversion is based on the time zone of the operating system where the CODESYS is running. (default setting)
If you change the option, then the displayed timestamp is converted automatically. |
![]() | Exports the list contents to an xml file You can select the file name and location. |
![]() | Imports an XML file with log messages stored in the file system A separate window opens to display the log messages. |
This window is available for controllers with Version 3.5 SP22 and higher. Clicking the refresh button | |
| The application is connected to the controller and the time interval for displaying the logger messages can be configured. |
Start | Start of the time interval when log messages are displayed The specified time can be changed manually or in the expandable calendar. |
End | End of the time interval when log messages are displayed The specified time can be changed manually or in the expandable calendar. |
Selection | The log messages for the selected time interval are displayed. If the end time is before the start time, then this is indicated by the |
Last hour | The log messages from the past hour are displayed. The displayed time interval will update accordingly. |
Today | The log messages for today (24 hours) are displayed. The displayed time interval will update accordingly. |
| The two times Start and End will be postponed by 24 hours. The displayed time interval will update accordingly. |
| The two times Start and End will be postponed by one hour. The displayed time interval will update accordingly. |
Next | Can be activated when more than 10,000 logger messages are available. Clicking this button will display the remaining, previously unseen logger messages (max. 10,000). |
| The two times Start and End will be advanced by 24 hours. The displayed time interval will update accordingly. |
| The two times Start and End will be advanced by one hour. The displayed time interval will update accordingly. |
Display window with log file | Tabular display of the log messages Ten thousand log messages are displayed per page. |
Severity |
|
Time Stamp | Date and time of the development system or of the runtime system) Example: |
Description | Description of the event Example: |
Component | Runtime component where the reported event occurred |
Auto-Scrolling | Displays whether auto-scrolling is enabled (ON) or disabled (OFF)
TipHint: Click the |
Note
Error checking
For exceptions with the *SOURCEPOSITION* description, the affected function opens in the editor by double-clicking it or by means of the Display Source Code in Editor command in the context menu. The cursor jumps to the line that is causing the error. You can also perform this diagnosis when you have the CODESYS project archive, including the download information files and the exported log file.
When the affected function is protected, then the following message appears: "The source code is not available for <function name>."
Tip
If a VendorException is reported, then a manufacturer-specific exception error has occurred in the CODESYS runtime. Contact the PLC manufacturer for more information.
























